-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Infer OpenCensus resource type based on OpenTelemetry's semantic conventions #1462
Infer OpenCensus resource type based on OpenTelemetry's semantic conventions #1462
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1462 +/- ##
==========================================
+ Coverage 90.90% 90.92% +0.01%
==========================================
Files 239 239
Lines 16692 16702 +10
==========================================
+ Hits 15174 15186 +12
+ Misses 1086 1085 -1
+ Partials 432 431 -1
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To be really explicit as to why this is needed: this ensures the case of OT SDK
-> OTLP
-> Collector
-> Exporter
(that uses OC internal data model and exports resource data based on OC conventions) will work without having to change the exporter.
@bogdandrutu could we cut a bugfix release with this in order to test it with a production setup ? I have a few customers waiting on it. Thanks ! |
@ocervell Note that you may use unreleased OpenTelemetry Collector (or contrib) Docker images with the |
@nilebox thank you |
Disclaimer: I have initially tried to fix this issue for Stackdriver exporter only (open-telemetry/opentelemetry-collector-contrib#581), but it seems generic enough to be part of the core.
Description:
Reverse mapping from OpenTelemetry's semantic conventions to OpenCensus resource type.
Since OpenTelemetry has switched to using semantic conventions over explicit resource types, the resource type may now be missing when converted to OpenCensus resource.
In that case we will try to infer the resource type based on documented conventions.
Link to tracking Issue:
The issue has been originally discussed in open-telemetry/opentelemetry-python#951 (comment), pointing to inconsistency between OpenCensus and OpenTelemetry which needs to be addressed.
Testing: Unit tests added for new functionality
Documentation: No documentation needed, we may just refer to the already documented semantic conventions.
/cc @james-bebbington